Error Codes for Alert Rule APIs
The following are the status code and the error description for the APIs.
Status Code |
Description |
|---|
200 |
- A successful response
- `{
“success”: true,
“data”: [
],
“message”: “string”
}`
|
200 |
- Duplicate Alert Rule Name
{“success”:false,”validationErrors”:{“name”:”Alertrule with the same name already exists”},”message”:”Invalid Request”}
|
200 |
- Wrong Alert Rule ID
{“success”:false,”error_code”:null,”message”:”AlertRule with ID: 682d91ea08598720b79eaaba doesn’t exist”}
|
200 |
- Duplicate Alert Rule Name
{“success”:false,”validationErrors”:{“name”:”Alertrule with the same name already exists”},”message”:”Invalid Request”}
|
422 |
- A validation error
- `{
“success”: false,
“validationErrors”: {
“additionalProp1”: “string”,
“additionalProp2”: “string”,
“additionalProp3”: “string”
},
“message”: “string”
}`
|
401 |
- Invalid Token
{“error”:”Signature verification failed”, “status_code” : 401, “success”: false}
|
401 |
- Expired Token
{“error”:”Signature has expired”, “status_code” : 401, “success”: false}
|
403 |
- Required scope is not present for accessing the API
{“error”:”Request out of the scope of the token”, “status_code” : 403, “success”: false}
|
400 |
- iss Claims is not self-signed
{“error”:”Could not map key ID to an authentic Public Key”, “status_code” : 400, “success”: false}
|
